Fix DST boundary issue occurring on Cloudflare env (fixes #108) #114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Daylight savings hack. Cloudflare Workers uses a different Date implementation than Node 20.x, which doesn't seem to respect DST boundaries the same way (see: #108).
To work around this, instead of adding 1 day, we add 25 hours every increment (intentionally overshooting), then grab the start of the day from that time, and repeat. This works in both Node 20.x and the production Cloudflare Workers environment.
NOTE: There's already a DST boundary test, but it was always passing since it was running in a Node environment.